The mobile operating system must produce audit records containing the severity level of each recorded event.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-32953	SRG-OS-000037-MOS-000013	SV-43351r1_rule		Low

Description
Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. Without sufficient information establishing what type of audit events occurred, investigation into the severity of events is severely hindered. As defined in RFC 5424 "The Syslog Protocol", event severity levels allow system administrators and IA personnel to more easily identify critical system issues.

Description

Operating system auditing capability is critical for accurate forensic analysis. Audit record content that may be necessary to satisfy the requirement of this control includes timestamps, source and destination addresses, user/process identifiers, event descriptions, success/fail indications, file names involved, and access control or flow control rules invoked. Without sufficient information establishing what type of audit events occurred, investigation into the severity of events is severely hindered. As defined in RFC 5424 "The Syslog Protocol", event severity levels allow system administrators and IA personnel to more easily identify critical system issues.

STIG	Date
Mobile Operating System Security Requirements Guide	2013-04-12

Details

Check Text ( C-41254r1_chk )
Review the audit logs for entries for the severity level of each recorded event. If any event in the log does not have an event severity level, this is a finding.

Fix Text (F-36868r1_fix)
Modify the audit configuration to include the severity level of events in audit records.